Methods and systems for managing employee-liable expenses

ABSTRACT

A method for managing payments made as part of an employee-liable expense reimbursement program is described. A plurality of employees are enrolled in the program and submit requests for reimbursement for expenses related to a service provided to the employees by a service provider for which the employees are liable. The method includes receiving, by the computer system, requests for reimbursement and aggregating the requests for reimbursement scheduled for payment within a predefined time period and associated with the service provider. The method also includes generating an invoice that includes a payment amount to be paid to the employee for subsequent payment to the service provider. The method also includes automatically requesting funds from an employer of the plurality of employees for the payment amount included in the invoice and electronically transferring funds associated with the employer to the service provider or alternatively, to the employee for subsequent payment to the service provider.

CROSS REFERENCE TO RELATED APPLICATIONS

This is a continuation-in-part of U.S. patent application Ser. No.13/469,341, filed May 11, 2012, which in turn claims the benefit of U.S.Provisional Application No. 61/605,008, filed Feb. 29, 2012, both ofwhich are hereby incorporated by reference in their entirety.

BACKGROUND OF THE INVENTION

The embodiments described herein relate generally to methods and systemsfor managing payment of bills, and more specifically to network-basedsystems and methods for managing expenses related to services providedto an employee by a service provider for which the employee is liable,wherein the employer provides a benefit to the employee by paying atleast a portion of the incurred expenses directly to the serviceprovider or alternatively directly to the employee.

Use of mobile communication devices has become increasingly common. Forexample, mobile devices facilitate communication with an employee of acorporation even when the employee is away from the corporation'soffices. For this and other reasons, corporations may desire use ofmobile devices by employees. Costs associated with mobile devicesinclude the cost of the mobile device (i.e., equipment costs) and thecost of the mobile service (i.e., a cellular usage plan). The cellularusage plan may include a talk portion and a data portion. For example,the plan may provide a user, for a first set monthly price, with anallotment of X minutes of talk time using the mobile device and of Ybytes of data transmission/reception. The cost of the data plan may beincluded within the first set monthly price or a separate data planprice.

It may be advantageous for the corporation to own the mobile devicesused by their employees and/or to pay for the service. These costs maybe referred to as a corporation-liable expense. Many companies enrolltheir employees in a company-wide shared cellular usage plan provided bya cellular service provider. Billing is simplified by having all of theemployees enrolled with a single cellular service provider. An employeealso can be required to return the mobile device to the corporation upontermination of their employment with the corporation if the corporationowns the mobile device. Furthermore, the corporation may be entitled todelete data stored on the mobile device upon termination of theemployment if the corporation owns the mobile device. Maintainingcontrol of the equipment and data is beneficial to the corporation;however, the corporation may not be able to meet employee requests foraccess to different types of equipment and service provided by differentcellular phone service providers. Furthermore, typically the corporationis responsible for customer service, provisioning of the mobile devices,and other support functions related to a corporate owned and paid mobilephone service.

To satisfy employee requests for choice in their mobile device and/orplan, the corporation may provide employees with a mobile phone benefit.For example, the corporation may agree to pay for an employee's mobileusage plan; however, ultimately the employee is liable to a mobileservice provider (i.e., an employee-liable expense). The corporation mayreimburse the employee upon receipt of a reimbursement request from theemployee. Manual entry and processing of the reimbursement requests isburdensome and does not provide an inventory of mobile devices beingpaid for by the corporation. Furthermore, there is no connection betweenthe reimbursement requests and a human resources department of thecorporation, where, for example, records of the corporation's agreementsregarding payment of employee mobile expenses and a current employeestatus typically are maintained.

Alternatively, the corporation may provide the employee with a monthlystipend included in a pay check and earmarked for payment of mobilephone expenses. Reimbursement of mobile phone expenses in this mannerdoes not provide the corporation with an inventory of mobile devices andalso does not provide a connection between requests for reimbursementand the corporation's human resources department. Furthermore, anemployee stipend of this sort may have negative tax consequences whencompared to payments made by the corporation in response to areimbursement request. For example, an employee stipend may be taxed asincome to the employee. In contrast, a payment made by the corporationin response to a reimbursement request may be designated as a businessexpense. However, by paying for the mobile device expenses, thecorporation may maintain the right to delete data stored on the mobiledevice of an employee upon termination of the employee.

Accordingly, it is desirable to have a network-based system and methodof managing employee-liable expenses by an employer that will addressthe disadvantages of the known systems described above.

BRIEF DESCRIPTION OF THE INVENTION

In one embodiment, a computer-based method is provided, for managingpayments made as part of an employee-liable expense reimbursementprogram, wherein a plurality of employees are enrolled in the programand submit requests for reimbursement for expenses related to a serviceprovided to the employees by a service provider for which the employeesare liable. The method is implemented using a computer system thatincludes a processor and a memory device. The method includes receiving,by the computer system, requests for reimbursement. The method furtherincludes aggregating the requests for reimbursement scheduled forpayment within a predefined time period and associated with the serviceprovider. The method further includes generating an invoice thatincludes a payment amount to be paid to first service provider. Themethod further includes automatically requesting funds from an employerof the plurality of employees for the payment amount included in theinvoice. The method further includes electronically transferring fundsassociated with the employer to one of the service provider and theemployee.

In another embodiment, one or more non-transitory computer-readablestorage media having computer-executable instructions embodied thereonare provided. When executed by at least one processor, thecomputer-executable instructions cause the processor to receive requestsfor reimbursement from employees enrolled in an employee-liable expensereimbursement program. The computer-executable instructions furthercause the processor to aggregate the requests for reimbursementscheduled for payment within a predefined time period and associatedwith the service provider. The computer-executable instructions furthercause the processor to generate an invoice that includes a paymentamount to be paid to first service provider. The computer-executableinstructions further cause the processor to automatically request fundsfrom an employer of the plurality of employees for the payment amountincluded in the invoice. The computer-executable instructions furthercause the processor to electronically transfer funds associated with theemployer to one of the service provider and the employee.

In yet another embodiment, a computer system is provided for managingpayments made as part of an employee-liable expense reimbursementprogram, wherein a plurality of employees are enrolled in the programand submit requests for reimbursement for expenses related to servicesprovided to the employees by a service provider for which the employeesare liable. The computer system includes a processor and a memorydevice. The processor is operable to execute instructions stored in thememory device causing the processor to receive requests forreimbursement from employees enrolled in an employee-liable expensereimbursement program. The computer-executable instructions furthercause the processor to aggregate the requests for reimbursementscheduled for payment within a predefined time period and associatedwith the service provider. The computer-executable instructions furthercause the processor to generate an invoice that includes a paymentamount to be paid to first service provider. The computer-executableinstructions further cause the processor to automatically request fundsfrom an employer of the plurality of employees for the payment amountincluded in the invoice. The computer-executable instructions furthercause the processor to electronically transfer funds associated with theemployer to one of the service provider and the employee.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic diagram illustrating an exemplary multi-partypayment system that includes an expense manager.

FIG. 2 is a simplified block diagram of an exemplary embodiment ofserver architecture of an expense management system for processing ofemployee-liable expenses, in accordance with one embodiment of thepresent invention.

FIG. 3 is an expanded block diagram of an exemplary embodiment of serverarchitecture of the expense management system shown in FIG. 2.

FIG. 4 illustrates an exemplary configuration of a client system shownin FIGS. 2 and 3.

FIG. 5 illustrates an exemplary configuration of a server system shownin FIGS. 2 and 3.

FIG. 6 is a flow chart of an exemplary method for managing payments madeby an employer to accounts with a service provider for which an employeeis liable, or optionally to an employee directly, using the expensemanagement system shown in FIGS. 2 and 3.

FIG. 7 is a flow chart of an exemplary method of receiving data from anemployer implemented using the expense management system shown in FIGS.2 and 3.

FIG. 8 is a flow chart of an exemplary method for registering anemployee in the reimbursement program implemented using the expensemanagement system shown in FIGS. 2 and 3.

FIG. 9 is a flow chart of an exemplary method for registering a devicein the reimbursement program implemented using the expense managementsystem shown in FIGS. 2 and 3.

FIG. 10 is a flow chart of an exemplary method for determining whichemployee-liable expense reimbursement level an employee is eligible toreceive using the expense management system shown in FIGS. 2 and 3.

FIG. 11 is a flow chart of an exemplary method for receiving a requestfor reimbursement from an employee implemented using the expensemanagement system shown in FIGS. 2 and 3.

FIG. 12 is a flow chart of an exemplary method for approving areimbursement request from an employee implemented using the expensemanagement system shown in FIGS. 2 and 3.

FIG. 13 is a flow chart of an exemplary method for distributing paymentsto employee-liable service provider accounts using the expensemanagement system shown in FIGS. 2 and 3.

DETAILED DESCRIPTION OF THE INVENTION

The methods and systems for managing payment of employee-liable expensesdescribed herein allow a payment to be made by an employer, or on behalfof an employer, to a service provider to which an employee is liable, oroptionally to the employee directly. The payment is made by the employeras a benefit to the employee. More specifically, the methods and systemsdescribed herein facilitate, for example, distributing payments from theemployer directly to accounts with a service provider for which theemployee is liable, or optionally, directly to an employee. In theexemplary embodiment, an expense manager receives data from the employerand data from the employee, enrolls the employee in a reimbursementprogram, generates an invoice for employer approval, and distributes apayment to the service provider. The expense manager utilizes an expensemanagement system to perform the processes described herein. In someembodiments, the expense manager is a separate entity from the employer,that is, a third-party who provides expense management services. Inother embodiments, the functions of the expense manager and the expensemanagement system are included within, and performed by, the employer.The expense management system provides the employer with reports ofemployee-liable expenses paid by the employer and an inventory ofemployee-liable devices. The methods and systems described herein allowan employer to provide a reimbursement benefit associated withemployee-liable devices and provide the employer with an inventory andrecords typically only available to an employer with respect toemployer-liable devices. In a specific example, the employee-liablereimbursement program described herein allows an employer to provide amobile phone benefit to employees, without assuming responsibilities forcustomer service and/or support functions, and while employees are ableto choose service providers, devices, plans, and/or features.

In a specific embodiment, the systems and processes described hereincredit an employee's personal account with a service provider for use ofa personal mobile device. A technical effect of the systems andprocesses described herein include at least one of: (a) receiving, bythe computer system, requests for reimbursement; (b) aggregating therequests for reimbursement scheduled for payment within a predefinedtime period and associated with the service provider; (c) generating aninvoice that includes a payment amount to be paid to a first serviceprovider; (d) automatically requesting funds from an employer of theplurality of employees for the payment amount included in the invoice;(e) electronically transferring funds associated with the employer toone of the service provider and the employee; (f) transferring fundsdirectly to the employee; (g) receiving, by the computer system,approval of the invoice from the employer; (h) storing a reimbursementrecord for each of the plurality of employees enrolled in the program,wherein the reimbursement record includes at least one of areimbursement amount, an employee account identifier, and a serviceprovider account identifier; (i) generating the invoice based at leastpartially on the reimbursement amounts included within the reimbursementrecords; (j) including within the generated invoice details as to aportion of the payment amount to be paid to the service providerassociated with each employee of the plurality of employees; (k)providing data to the employer that identifies a portion of the paymentamount associated with at least one of a cost center within the employerand a geographic location of the employees; (l) providing the data tothe employer comprises providing the employer with access to a webpage,wherein the webpage provides the employer with options on how toorganize the data associated with the employer that is stored by thememory device; (m) providing the invoice to the employer; (n)transmitting the invoice to the employer, wherein the invoice has apredefined format that is compatible with software utilized by theemployer; (o) providing the employer with access to the invoice, whereinthe invoice has a predefined format that is compatible with softwareutilized by the employer; (p) receiving, by the computer system, dataassociated with a request for reimbursement from an employee of theplurality of employees; (q) generating, by the computer system, arequest for reimbursement based at least partially on the data receivedfrom the employee; (r) requesting approval, from the employer, of therequest for reimbursement; (s) receiving approval of the request forreimbursement; and (t) initiating recurring reimbursement programpayments for approved requests for reimbursement.

In one embodiment, a computer program is provided, and the program isembodied on a computer-readable medium and utilizes a Structured QueryLanguage (SQL) with a client user interface front-end for administrationand a web interface for standard user input and reports. In an exemplaryembodiment, the system is web enabled and is run on a business-entityintranet. In yet another embodiment, the system is fully accessed byindividuals having an authorized access outside the firewall of thebusiness-entity through the Internet. In a further exemplary embodiment,the system is being run in a Windows® environment (Windows is aregistered trademark of Microsoft Corporation, Redmond, Wash.). In yetanother embodiment, the system is run on a mainframe environment and aUNIX® server environment (UNIX is a registered trademark of X/OpenCompany Limited located in Reading, Berkshire, United Kingdom). Theapplication is flexible and designed to run in various differentenvironments without compromising any major functionality. In someembodiments, the system includes multiple components distributed among aplurality of computing devices. One or more components may be in theform of computer-executable instructions embodied in a computer-readablemedium.

The systems and methods are not limited to the specific embodimentsdescribed herein. In addition, components of each system and each methodcan be practiced independent and separate from other components andmethods described herein. Each component and method also can be used incombination with other components and processes.

FIG. 1 is a schematic diagram 10 illustrating an exemplary multi-partypayment system 12 that includes an expense manager 14. Expense manager14 enables payment of employee-liable expenses by an employer, forexample, employer 20. In the exemplary embodiment, expense manager 14includes an expense management system 16 configured to perform theprocesses described herein. Furthermore, in the exemplary embodiment,expense manager 14 is a separate entity from employer 20, that is, athird-party who provides expense management services. In an alternativeembodiment, the functions of expense manager 14 and expense managementsystem 16 are included within, and performed by, employer 20. Paymentsystem 12 also includes a plurality of service providers 28, forexample, a first service provider 30, a second service provider 32, anda third service provider 34. Although illustrated as including threeservice providers, payment system 12 may include any suitable number ofservice providers that allows payment system 12 to function as describedherein.

Employer 20 may include a corporation, a charitable group, and/or anyother organization that employs a plurality of employees 40.Furthermore, the employees 40 may be independent contractors or in asimilar relationship with employer 20. As part of an agreement withemployees 40 (e.g., as part of an employment agreement), employer 20 mayagree to reimburse at least a portion of an employee-liable expense.Examples of employee-liable expenses include, but are not limited to,mobile phone expenses, auto loan/lease expenses, internet serviceprovider expenses, and/or any other repeating expense that an employeemay be contractually obliged to pay that may also relate to or be usedas part of the employee's employment. In the exemplary embodiment, afirst employee 42 of the plurality of employees 40 is a party to acontract with first service provider 30. For example, first serviceprovider 30 may be a first cellular service provider. First employee 42may be enrolled in a mobile device usage plan offered by first serviceprovider 30 and required to pay for the mobile device usage plan on amonthly basis.

In the exemplary embodiment, a second employee 44 of the plurality ofemployees 40 is a party to a contract with second service provider 32.Furthermore, a third employee 46 of the plurality of employees 40 is aparty to a contract with third service provider 34. Although illustratedas including three employees each being a party to a contract with adifferent service provider, the plurality of employees 40 may includeany number of employees being party to contracts with any number ofdifferent service providers. Typically, payment system 12 will include afirst plurality of employees having contracts with first serviceprovider 30, a second plurality of employees having contracts withsecond service provider 32, and a third plurality of employees havingcontracts with third service provider 34. In the exemplary embodiment,employer 20 agrees to reimburse each of employees 40 for anemployee-liable expense, but does not limit the service provider theemployee is able to select to provide the service associated with theexpense. Alternatively, the plurality of employees 40 may select from alist of approved service providers provided by employer 20.

In the exemplary embodiment, expense management system 16 allowsemployer 20 to offer an employee-liable reimbursement program toemployees 40. In the exemplary embodiment, expense management system 16provides the option to employees 40, to have reimbursements paiddirectly to service providers 28, or directly to employees 40, forexample via direct deposit to accounts associated with employees 40. Inone embodiment, the right to exercise the option resides with employer20. In another embodiment, employees 40 individually have the right tochoose to be reimbursed directly. In addition, in one embodiment,expense management system 16 is configured so that for some of employees40, reimbursements are made directly to one or more service providers28, and for others of employees 40, reimbursements are made directly tothose employees 40. Once first employee 42 is enrolled in theemployee-liable reimbursement program, expense management system 16administers a periodic distribution of payments 50 directly to firstservice provider 30, and more specifically, directly to an account withfirst service provider 30 associated with first employee 42. In theexemplary embodiment, the payments are distributed to first serviceprovider 30 via ACH/CTX payment transactions. An amount and frequency ofpayments 50 is predetermined based on a reimbursement level in whichfirst employee 42 is eligible. The reimbursement level is defined basedon policies developed by employer 20. Although described herein as areimbursement for an employee-liable expense, payments made by expensemanager 14 may also be referred to as a credit to the account with firstservice provider 30 associated with first employee 42, in a situation inwhich the option to have payments made directly to first serviceprovider 30 has been exercised.

Similarly, once second employee 44 is enrolled in the employee-liablereimbursement program, expense management system 16 administers aperiodic distribution of payments 52 directly to second service provider32, and more specifically, directly to an account with second serviceprovider 32 associated with second employee 44, or to second employee 44(for example to an account associated with second employee 44), if thatoption is being exercised. Furthermore, once third employee 46 isenrolled in the employee-liable reimbursement program, expensemanagement system 16 administers a periodic distribution of payments 54directly to third service provider 34, and more specifically, directlyto an account with third service provider 34 associated with thirdemployee 46. Alternatively, if the option for direct payment toemployees 40 is exercised, expense management system 16 administersperiodic distribution of payments directly to one or more of employees42, 44, and/or 46.

In the exemplary embodiment, expense management system 16 providesemployer 20 with at least one report 60. Report 60 may include, but isnot limited to, a status of payments made to service providers 28, anamount paid to one or more of service providers 28 and/or one or more ofemployees 42-46, and amounts reimbursed for each of employees 40.Furthermore, report 60 provides an accounting of each payment made byexpense management system 16 and other reporting functions necessary forauditing the validity of each payment. For example, report 60 may beincluded within an automated general ledger upload file for recordingemployee-liable reimbursement program payments.

In the exemplary embodiment, report 60 also includes an inventory andmonthly validation of employee-liable devices (also referred to asindividual responsibility units (IRUs)) and accounts. For example, theinventory of employee-liable devices provides a list of mobile phonenumbers associated with these employee-liable devices that is typicallyunavailable to employer 20.

In the exemplary embodiment, expense manager 14 requests funds 62, to bepaid to one or more of service providers 28 and/or one or more ofemployees 40, from employer 20. Funds 62 either reimburses expensemanager 14 for payments made to service providers 28, or provide expensemanager 14 with the money to be paid to service providers 28. Funds 62may also include a fee charged by expense manager 14 for use of expensemanagement system 16. In the exemplary embodiment, funds 62 areelectronically requested and employer 20 is also provided with anautomated general ledger upload file for recording the employee-liablepayments. After approving the funds request, employer 20 transfers funds62 to expense manager 14.

In the exemplary embodiment, expense management system 16 matchespayments, for example, payments 50, 52, and 54, to human resourcerecords provided by employer 20 to ensure payments are made only onbehalf of, and/or to, valid employees. Furthermore, matching payments50, 52, and 54 to human resource records ensures employees 42, 44, and46 remain eligible for the level of reimbursement provided by payments50, 52, and 54.

FIG. 2 is a simplified block diagram of an exemplary system 100 inaccordance with one embodiment of the present invention. System 100 isconfigured to implement the data flow shown in FIG. 1. In oneembodiment, system 100 is an expense management system, for example,expense management system 16 (shown in FIG. 1), used to facilitatedistribution of payments from an employer directly to a serviceprovider, and more specifically, directly to accounts with the serviceprovider for which an employee is liable, and/or to employees. Inaddition, system 100 is operable as a reporting and inventory system,which can be utilized by employer 20 (shown in FIG. 1) to monitorexpenses related to employee-liable devices.

More specifically, in the exemplary embodiment, system 100 includes aserver system 112, and a plurality of client sub-systems, also referredto as client systems 114, connected to server system 112. In oneembodiment, client systems 114 are computers including a web browser,such that server system 112 is accessible to client systems 114 usingthe Internet. Client systems 114 are interconnected to the Internetthrough many interfaces including a network, such as a local areanetwork (LAN) or a wide area network (WAN), dial-in-connections, cablemodems and special high-speed ISDN lines. Client systems 114 could beany device capable of interconnecting to the Internet including aweb-based phone, personal digital assistant (PDA), or other web-basedconnectable equipment. A database server 116 is connected to a database120 or other memory device containing information on a variety ofmatters, as described below in greater detail. In one embodiment,centralized database 120 is stored on server system 112 and can beaccessed by potential users at one of client systems 114 by logging ontoserver system 112 through one of client systems 114. In an alternativeembodiment, database 120 is stored remotely from server system 112 andmay be non-centralized.

Database 120 stores employer-provided data and employee-provided datarelated to an employee-liable device reimbursement program, including,but not limited to, a list of employees eligible to participate in theemployee-liable device reimbursement program provided by the employer,eligibility requirements for reimbursement at a plurality ofreimbursement levels, an employee-liable device identifier provided bythe employee, and a service provider identifier provided by theemployee. Database 120 may also be utilized to store records ofdistributions made as part of the employee-liable device reimbursementprogram and employee-liable device inventory data including, but notlimited to, device identifiers.

FIG. 3 is an expanded block diagram of an exemplary embodiment of aserver architecture of a system 122 in accordance with one embodiment ofthe present invention. Components in system 122, identical to componentsof system 100 (shown in FIG. 2), are identified in FIG. 3 using the samereference numerals as used in FIG. 2. System 122 includes server system112 and client systems 114. Server system 112 further includes databaseserver 116, an application server 124, a web server 126, a fax server128, a directory server 130, and a mail server 132. A disk storagedevice 134 is coupled to database server 116 and directory server 130.Servers 116, 124, 126, 128, 130, and 132 are coupled in a local areanetwork (LAN) 136. In addition, a system administrator's workstation138, a user workstation 140, and a supervisor's workstation 142 arecoupled to LAN 136. Alternatively, workstations 138, 140, and 142 arecoupled to LAN 136 using an Internet link or are connected through anIntranet.

Each of workstations 138, 140, and 142 may be any computing device thatincludes a web browser, for example, but not limited to, a personalcomputer, a laptop computer, a tablet computer, and/or a mobile phone.Although the functions performed at the workstations typically areillustrated as being performed at respective workstations 138, 140, and142, such functions can be performed at one of many computing devicescoupled to LAN 136. Workstations 138, 140, and 142 are illustrated asbeing associated with separate functions only to facilitate anunderstanding of the different types of functions that can be performedby individuals having access to LAN 136.

Server system 112 is configured to be communicatively coupled to variousindividuals, including employees 144 and to third parties, e.g., accountholders, customers, auditors, etc., 146 using an internet serviceprovider (ISP) Internet connection 148. The communication in theexemplary embodiment is illustrated as being performed using theInternet, however, any other wide area network (WAN) type communicationcan be utilized in other embodiments, i.e., the systems and processesare not limited to being practiced using the Internet. In addition, andrather than WAN 150, LAN 136 could be used in place of WAN 150.

In the exemplary embodiment, any authorized individual having aworkstation 154 can access system 122. At least one of the clientsystems includes a manager workstation 156 located at a remote location.Workstations 154 and 156 are personal computers having a web browser.Also, workstations 154 and 156 are configured to communicate with serversystem 112. Furthermore, fax server 128 communicates with remotelylocated client systems, including a client system 156 using a telephonelink. Fax server 128 is configured to communicate with other clientsystems 138, 140, and 142 as well.

FIG. 4 illustrates an exemplary configuration of a user computing device202 operated by a user 204. User computing device 202 may include, butis not limited to, client systems 114, 138, 140, and 142, workstation154, and manager workstation 156. User computing device 202 includes aprocessor 206 for executing instructions. In some embodiments,executable instructions are stored in a memory area 210. Processor 206may include one or more processing units (e.g., in a multi-coreconfiguration). Memory area 210 is any device allowing information suchas executable instructions and/or written works to be stored andretrieved. Memory area 210 may include one or more computer readablemedia.

User computing device 202 also includes at least one media outputcomponent 212 for presenting information to user 204. Media outputcomponent 212 is any component capable of conveying information to user204. In some embodiments, media output component 212 includes an outputadapter such as a video adapter and/or an audio adapter. An outputadapter is operatively coupled to processor 206 and operativelycoupleable to an output device such as a display device (e.g., a liquidcrystal display (LCD), organic light emitting diode (OLED) display, or“electronic ink” display) or an audio output device (e.g., a speaker orheadphones).

In some embodiments, user computing device 202 includes an input device220 for receiving input from user 204. Input device 220 may include, forexample, a keyboard, a pointing device, a mouse, a stylus, a touchsensitive panel (e.g., a touch pad or a touch screen), a gyroscope, anaccelerometer, a position detector, or an audio input device. A singlecomponent such as a touch screen may function as both an output deviceof media output component 212 and input device 220.

User computing device 202 may also include a communication interface222, which is communicatively coupleable to a remote device such asserver system 112. Communication interface 222 may include, for example,a wired or wireless network adapter or a wireless data transceiver foruse with a mobile phone network (e.g., Global System for Mobilecommunications (GSM), 3G) or other mobile data network (e.g., WorldwideInteroperability for Microwave Access (WIMAX)).

Stored in memory area 210 are, for example, computer readableinstructions for providing a user interface to user 204 via media outputcomponent 212 and, optionally, receiving and processing input from inputdevice 220. A user interface may include, among other possibilities, aweb browser and client application. Web browsers enable users, such asuser 204, to display and interact with media and other informationtypically embedded on a web page or a website from server system 112. Aclient application allows user 204 to interact with a server applicationfrom server system 112.

FIG. 5 illustrates an exemplary configuration of a server computingdevice 300 such as server system 112 (shown in FIG. 2). Server computingdevice 300 may include, but is not limited to, database server 116,application server 124, web server 126, fax server 128, directory server130, and mail server 132. Server computing device 300 also includes aprocessor 302 for executing instructions. Instructions may be stored ina memory area 310, for example. Processor 302 may include one or moreprocessing units (e.g., in a multi-core configuration).

Processor 302 is operatively coupled to a communication interface 312such that server computing device 300 is capable of communicating with aremote device such as user computing device 202 (shown in FIG. 4) oranother server computing device 300. For example, communicationinterface 312 may receive requests from user computing device 202 viathe Internet, as illustrated in FIG. 3.

Processor 302 may also be operatively coupled to a storage device 134.Storage device 134 is any computer-operated hardware suitable forstoring and/or retrieving data. In some embodiments, storage device 134is integrated in server computing device 300. For example, servercomputing device 300 may include one or more hard disk drives as storagedevice 134. In other embodiments, storage device 134 is external toserver computing device 300 and may be accessed by a plurality of servercomputing devices 300. For example, storage device 134 may includemultiple storage units such as hard disks or solid state disks in aredundant array of inexpensive disks (RAID) configuration. Storagedevice 134 may include a storage area network (SAN) and/or a networkattached storage (NAS) system.

In some embodiments, processor 302 is operatively coupled to storagedevice 134 via a storage interface 320. Storage interface 320 is anycomponent capable of providing processor 302 with access to storagedevice 134. Storage interface 320 may include, for example, an AdvancedTechnology Attachment (ATA) adapter, a Serial ATA (SATA) adapter, aSmall Computer System Interface (SCSI) adapter, a RAID controller, a SANadapter, a network adapter, and/or any component providing processor 302with access to storage device 134.

FIG. 6 is a flow chart 400 of an exemplary method 410 for managingpayments made by an employer, for example, employer 20 (shown in FIG.1), to accounts with a service provider for which an employee is liable,for example, first service provider 30 (shown in FIG. 1). In theexemplary embodiment, an expense management system, for example, system100 (shown in FIG. 2) and/or system 122 (shown in FIG. 3), is configuredto perform method 410. In the exemplary embodiment, method 410 includesstoring 418 a plurality of employee-liable expense reimbursement levelsfor use within an employee-liable reimbursement program. In theexemplary embodiment, the employee-liable expense reimbursement levelsare predefined and stored within a memory device, for example, storagedevice 134 (shown in FIG. 3). As described above, the employee-liablereimbursement program facilitates distribution of electronic paymentsfrom employer 20 to an employee-liable service provider account. In theexemplary embodiment, the reimbursement levels are based at leastpartially on policies developed by employer 20. Furthermore, in theexemplary embodiment, an expense management system, for example, expensemanagement system 16 (shown in FIG. 1), manages the employee-liablereimbursement program.

In the exemplary embodiment, method 410 also includes receiving 420employee data from at least one of employer 20 and an employee ofemployer 20, for example, employee 42 (shown in FIG. 1). In theexemplary embodiment, method 410 also includes enrolling 422 employee 42in the reimbursement program. In the exemplary embodiment, enrolling 422includes determining 426 if employee 42 is eligible to register in thereimbursement program (see FIG. 8), determining 428 if a deviceassociated with employee 42 is eligible for reimbursement (see FIG. 9),and determining 430 a level of payment to be made to a service provideraccount associated with employee 42 (see FIG. 10). In the exemplaryembodiment, method 410 also includes processing 432 a request forreimbursement from employee 42 and distributing 434 a payment to theemployee-liable service provider account, or, if the option for directpayment to employee 42 has been selected, distributing 436 a payment tothe employee.

FIG. 7 is a flow chart 450 of an exemplary method of receiving 420employee data from employer 20 (shown in FIG. 1). The data received 420from employer 20 is also referred to herein as a human resources (HR)feed since typically, a human resources (HR) department of employer 20has access to employee information and provides the employee informationto expense management system 16. For example, the HR feed may beprovided by a human resource information system (HRIS) and/or by using alightweight directory access protocol (LDAP), and/or in any othersuitable manner that allows expense management system 16 to function asdescribed herein. In the exemplary embodiment, expense management system16 provides 460 employer 20 with an electronic form that requests theemployer-provided data required to implement the employee-liablereimbursement program. The HR feed includes data from which expensemanagement system 16 creates an HR profile table. The HR profile tableincludes a record for each employee identified by employer 20 as beingeligible to participate in the reimbursement program. The recordincludes at least an employee identifier, for example, but not limitedto, an electronic mail (e-mail) address and/or an employeeidentification number.

In the exemplary embodiment, expense management system 16 receives 462 afile containing the employer-provided data (e.g., the HR feed). Theemployer-provided data includes, but is not limited to, employeeidentifiers (e.g., employee identification numbers) and/or employeee-mail addresses. The employer-provided data may also include amanager/approver identifier and contact data (e.g., e-mail address) forthe manager/approver. Each employee eligible to participate in thereimbursement program is assigned a manager/approver tasked withreviewing requests for reimbursement submitted by the employee. Expensemanagement system 16 uses the contact data to request approval of arequest for reimbursement from the employee. Moreover, the HR feed mayalso include a cost center and/or a geographic location associated withthe employee. This data allows expense management system 16 to providerecords to employer 20 that are organized and/or sorted by cost centerand/or geographic location.

In the exemplary embodiment, expense management system 16 creates 464 atable of employee profiles from the employer-provided data. This tableis referred to herein as an HR profile table. In order to preventcreation of duplicate entries within the HR profile table, expensemanagement system 16 compares 466 the employer-provided data topreviously stored data. If the employer-provided data includes dataassociated with an employee whose employee identifier is alreadyincluded within the HR profile table, expense management system 16updates the employee's record within the HR profile table. The updatemay include an update to the employee's employment status, jobdescription, and/or any other type of employee data that is used todetermine eligibility in the reimbursement program. If an employeeidentifier associated with an employee not included in the HR profiletable is included in the employer-provided data, expense managementsystem 16 creates 464 a record for that employee within the HR profiletable.

FIG. 8 is a flow chart 580 of an exemplary method for determining 426 ifan employee, for example, employee 42 (shown in FIG. 1), is eligible toregister in the reimbursement program. As described above, enrolling 422(shown in FIG. 6) employee 42 in the reimbursement program includesdetermining 426 if employee 42 qualifies for registration in thereimbursement program. In the exemplary embodiment, expense managementsystem 16 determines 426 that employee 42 qualifies for registration inthe reimbursement program when employee 42 completes an employeeregistration process. The registration process includes activating anemployee account within expense management system 16 (shown in FIG. 1).An employee is enrolled in the reimbursement program once an employeeaccount is activated within expense management system 16.

In the exemplary embodiment, employee 42 accesses 600 a registrationwebpage using a client encrypted key and an employee identifier/passwordcombination. For example, employer 20 and/or expense manager 14 mayprovide employee 42 with an electronic invitation to join thereimbursement program. The electronic invitation includes the clientencrypted key and a link to the registration webpage. The clientencrypted key identifies to expense management system 16 that employee42 is an employee of employer 20. In the exemplary embodiment, the HRprofile table stored by expense management system 16 includes apreviously created record for employee 42. More specifically, expensemanagement system 16 has created 464 (shown in FIG. 7) a record foremployee 42 within the HR profile table from data provided by employer20 in the HR feed provided to expense management system 16. Includingdata associated with employee 42 within the HR feed allows expensemanagement system 16 to automatically approve a registration requestsubmitted by employee 42. In an alternative embodiment, employer 20 hasnot provided data associated with employee 42 within the HR feed, andtherefore, expense management system 16 has not created a record foremployee 42 within the HR profile table. If a record of employee 42 isnot included in the HR profile table, expense management system 16 mustobtain approval from employer 20 of the request for registrationsubmitted by employee 42.

More specifically, in the exemplary embodiment expense management system16 determines 612 if an HR feed has been received from employer 20. Ifan HR feed has been received, expense management system 16 compares 466the employee identifiers included within the HR feed with employeeidentifiers that already exist in the HR profile table previouslycreated by expense management system 16 from data included in apreviously received HR feed. If an employee record already exists in theHR profile table, expense management system 16 determines 616 if theemployee associated with the employee record has previously registeredin the reimbursement program. If the employee has already registered,expense management system 16 updates 618 the employment status of theemployee from data included within the most recent HR feed. Updating theemployment status ensures that reimbursement payments are only providedfor employees with a proper employment status (e.g., no payments madefor terminated employees). Updating the records within the HR profiletable periodically with data provided by the human resources departmentof employer 20 provides an automatic cross-check of at least one expenseof employer 20 with current human resource data. The human resourcedepartment and financial departments of an employer typically areseparate, with no convenient means to electronically exchange data ormatch expenses associated with an employee to a current employmentstatus of the employee.

If there is employee data in the HR feed associated with employees notincluded in the HR profile table previously created by expensemanagement system 16, expense management system 16 creates 620 recordscorresponding to the additional employee data within the HR profiletable and marks the records as valid. Once expense management system 16creates 620 records corresponding to the additional employee data,expense management system 16 also creates 622 a temporary password andprovides the temporary password to the employees associated with theadditional employee data, for example, via e-mail. Furthermore, if dataincluded in the HR feed is associated with employees already includedwithin the HR profile table, but who have not previously registered inthe reimbursement program, expense management system 16 also creates 622a temporary password and provides the temporary password to theunregistered employees.

As described above, employee 42 accesses 600 a registration webpageusing a client encrypted key provided by at least one of employer 20 andexpense manager 14, and an employee identifier/password combination. Theregistration webpage facilitates registering employee 42 in thereimbursement program, and if previously registered, allows employee 42to access an account webpage customized for employee 42 (i.e., a “MyAccount Page”). If employee 42 indicates (e.g., by selecting a “forgotpassword” selection provided on the registration webpage) that they donot know their password, expense management system 16 generates 640 anew password and provides the new password to employee 42, for example,via e-mail. If employee 42 knows their password, employee 42 enters 642their employee identifier/password combination in order to login toexpense management system 16.

In the exemplary embodiment, expense management system 16 determines 650if the login information provided is encrypted and, if not, validates652 the login information. If the login information provided isencrypted, or if the login information provided is validated, expensemanagement system 16 determines 654 if employee 42 has previouslyvalidated the data from the HR feed. Expense management system 16displays the data from the HR feed associated with employee 42 toemployee 42 and asks employee 42 to confirm that the data is accurate(e.g., cost center and/or manager is correct, name is spelled correctly,etc.). If employee 42 indicates that the data is not accurate, expensemanagement system 16 transmits 656 a notification to employee 42instructing employee 42 to contact a manager to address the incorrectinformation. If employee 42 indicates that the data is accurate, expensemanagement system 16 marks the employee record in the HR profile tableassociated with employee 42 as validated.

If the employee record associated with employee 42 has been marked asvalidated, expense management system 16 determines 660 if employee 42has previously registered in the reimbursement program. If employee 42is already registered in the reimbursement program, expense managementsystem 16 provides 662 employee 42 with access to an account webpagecustomized for employee 42 (i.e., a “My Account Page”).

If employee 42 is validated, but has not previously registered in thereimbursement program, expense management system 16 retrieves 664profile data provided by employer 20 and included within the HR feed andpre-populates a registration form with the retrieved profile data.Employee 42 provides expense management system 16 with employee data bycompleting the registration form. Expense management system 16 provides670 employee 42 with the electronic registration form with some fieldspre-populated to include data received from employer 20. Employee datamay include, but is not limited to, employee name, employee identifier,geographic location of the employee, and/or a manager identifier (e.g.,e-mail address) associated with a manager to which the employee reports.

In the exemplary embodiment, employee 42 transmits the electronicregistration form to expense management system 16 after populating thefields contained therein. In the exemplary embodiment, expensemanagement system 16 determines if all required information has beenprovided by employee 42. For example, expense management system 16 maydetermine 680 if a valid manager identifier has been provided byemployee 42 and whether the manager associated with the manageridentifier has been identified by employer 20 as having approvalauthority. If a manager identifier associated with someone havingapproval authority has not been provided to expense management system16, expense management system 16 provides 670 the electronicregistration form to employee 42 with instructions to provide a validmanager identifier. Furthermore, if a manager identifier associated withsomeone having approval authority has been provided, expense managementsystem 16 may determine 682 if employee 42 has indicated approval of awireless policy created by employer 20 and/or expense manager 14.

Once employee 42 has provided all required information, expensemanagement system 16 determines 684 if any devices have been associatedwith employee 42. For example, expense management system 16 maydetermine 684 if employee 42 has previously registered any devices inthe reimbursement program. If employee 42 has not previously registeredany devices, employee 42 is provided 688 with a device registrationwebpage, through which employee 42 is able to register a device. Ifemployee 42 has previously registered a device, employee 42 is provided662 with access to the My Account Page.

FIG. 9 is a flow chart 800 of an exemplary method for determining 428 ifa device is eligible for reimbursement through the employee-liabledevice reimbursement program. Once the request for registration fromemployee 42 is approved 590 (see FIG. 8), expense management system 16determines 428 if costs incurred by employee 42 associated with a deviceused by employee 42 are eligible for reimbursement through thereimbursement program. In the exemplary embodiment, expense managementsystem 16 determines 428 that the device qualifies for reimbursementthrough the reimbursement program based on answers provided by employee42 during a device registration process. The device registration processincludes obtaining device data from employee 42. The device dataincludes, but is not limited to, data used to identify the device anddata used to determine if costs associated with the device areemployee-liable expenses or employer-liable expenses. Furthermore, thedevice registration process facilitates creating a device list for useby employer 20 in tracking employee-liable devices and/oremployer-liable devices.

In the exemplary embodiment, expense management system 16 requests 810that employee 42 provide an identifier associated with a device used byemployee 42. For example, employee 42 may provide a mobile phone numberassociated with a mobile phone used by employee 42. Employee 42 may alsoprovide other types of identification numbers including, but not limitedto, a mobile identification number (MIN), an electronic serial number(ESN), an international mobile equipment identity (IMEI) number, amobile equipment identifier (MEID), and/or any other unique identifierassigned to one specific device.

In the exemplary embodiment, expense management system 16 determines 812if a device associated with the provided identifier exists in a storedemployee-liable device inventory. For example, expense management system16 may already be storing device information associated withemployee-liable devices for employer 20. This device information isstored in the employee-liable device inventory. If expense managementsystem 16 determines 812 that a device associated with the providedidentifier exists in the stored employee-liable device inventory,expense management system 16 provides 814 an error message to employee42 indicating that the device may not be registered because the devicehas already been registered.

In the exemplary embodiment, if expense management system 16 determines812 that a device associated with the provided identifier does not existin the stored employee-liable device inventory, expense managementsystem 16 determines 816 if a device associated with the providedidentifier exists in an employer-liable device inventory. For example,expense management system 16 may also store information related toemployer-liable devices of employer 20. Employer-liable devices aredevices that employer 20 owns and is liable for associated costs. Ifexpense management system 16 determines 816 the device associated withthe provided identifier is in the employer-liable device inventory,expense management system 16 designates 818 the device as anemployer-liable device. Employer-liable devices are not eligible to beregistered in the employee-liable device reimbursement program sincecosts associated with employer-liable device are paid by employer 20using a different process. In the exemplary embodiment, expensemanagement system 16 requests 820 employee 42 provide answers toemployer-liable device inventory questions so that expense managementsystem 16 may create 822 a profile inventory record for the device. Theprofile inventory may include records for both employee-liable devicesand employer-liable devices. Although employer-liable devices are noteligible for the reimbursement program, expense management system 16creates 822 profile inventory records for the employer-liable devices inorder to provide employer 20 with a combined directory ofemployer-liable and employee-liable devices. The employer-liable deviceinformation requested by expense management system 16 may include, butis not limited to, a device type, a device description, and/or a devicetracking number.

If expense management system 16 determines 816 that a device associatedwith the provided identifier does not exist in the employer-liableinventory, expense management system 16 requests 830 billing informationfrom employee 42. For example, expense management system 16 may ask ifthe device is billed directly to employee 42. If the device is billeddirectly to employee 42, expense management system 16 designates 832 thedevice as an employee-liable/expensed device. An employee is personallyliable for costs associated with an employee-liable device.

Furthermore, if the device is not billed directly to employee 42,expense management system 16 determines 834 if the reason employee 42has not yet received an invoice for the device from a service provider,for example, service provider 30 (shown in FIG. 1) is that the device isnew. If employee 42 indicates to expense management system 16 that thedevice is not new, expense management system 16 designates 818 thedevice as an employer-liable device since invoices for the device aremost likely being issued to employer 20. If employee 42 indicates thatthe device is new, expense management system 16 requests 840 expensinginformation from employee 42. If employee 42 indicates that costsassociated with the device will be expensed, expense management system16 also designates 832 the device as an employee-liable/expensed device.If employee 42 indicates that costs associated with the device will notbe expensed, system 16 designates 842 the device as an invalid device.The device is designated 842 as an invalid device because informationprovided by employer 20 during the device registration is eithercontradictory or does not provide enough information for expensemanagement system 16 to determine if the device is an employee-liabledevice or an employer-liable device. Additional information, andtypically interaction between employer 20 and employee 42, is necessaryto resolve registration issues for a device designated 842 as invalid.

In the exemplary embodiment, once expense management system 16designates 832 the device as an employee-liable/expensed device, expensemanagement system 16 requests 844 employee 42 provide answers toemployee-liable inventory questions so that expense management system 16may create 822 a profile inventory record for the device. Theemployee-liable inventory information requested by expense managementsystem 16 may include, but is not limited to, a device type, a devicedescription, a device carrier (e.g., a service provider associated withthe device), a device model, a device make, and/or a device masteraccount number. In the exemplary embodiment, expense management system16 determines 846 if the device is an invalid device. For example,expense management system 16 analyzes the employee-liable inventoryinformation provided by employee 42 to identify contradictoryinformation and/or missing information that would require humaninteraction to resolve. The method of determining 428 if a device iseligible may be repeated, as employee 42 may seek to register more thanone device in the employee-liable expense reimbursement program. Forexample, employee 42 may be liable for expenses related to a mobilephone, expenses related to a tablet computing device (e.g., an iPad®,iPad® is a registered trademark of Apple, Inc.), and expenses related toa home computer (e.g., Internet access). Expense management system 16allows employee 42 to register multiple devices in the reimbursementprogram.

FIG. 10 is a flow chart 860 of an exemplary method for determining 430which employee-liable expense reimbursement level an employee, forexample, employee 42 (shown in FIG. 1), is eligible to have reimbursed.As described above, enrolling 422 (shown in FIG. 6) employee 42 in thereimbursement program includes determining 430 a level of payment to bemade to a service provider account associated with employee 42, or, if adirect employment payment option has been selected, to be made directlyto employee 42. In the exemplary embodiment, the employee-liable expensereimbursement level that an employee is eligible to have reimbursed isdetermined by expense management system 16 based on the employee'sresponses to a plurality of questions. In an alternative embodiment, theemployee-liable expense reimbursement level that an employee is eligibleto have reimbursed is provided to expense management system 16 byemployer 20, for example, within the HR feed. In another alternativeembodiment, the employee-liable expense reimbursement level that anemployee is eligible to have reimbursed is determined based on aposition the employee holds with employer 20, and a reimbursement levelprovided by employer 20 associated with that position. For example,employer 20 may provide expense management system 16 with a list of jobtitles and the reimbursement level associated with each of those jobtitles. Expense management system 16 determines 430 whichemployee-liable expense reimbursement level an employee is eligible tohave reimbursed based on the employee's job title.

In the exemplary embodiment, determining 430 which employee-liableexpense reimbursement level employee 42 is eligible to receive includesrequesting information from at least one of employee 42 and employer 20regarding the job employee 42 performs for employer 20, usage of thedevice by employee 42, and/or any other information that allows expensemanagement system 16 to execute the employee-liable reimbursementprogram policies developed by employer 20.

For example, expense management system 16 may provide 870 a plurality ofquestions 874 to at least one of employee 42 and employer 20. Expensemanagement system 16 determines 876 from the responses to thesequestions whether employee 42 is eligible to have a reimbursementpayment made to a service provider on their behalf, or, if a directemployee payment option has been selected, directly to employee 42, at afirst level 880, a second level 882, a third level 884, or a fourthlevel 886. Although described as including four levels, thereimbursement program may reimburse at any number of different levels.Furthermore, expense management system 16 may determine from theresponses to questions 874 that a device of employee 42 that is possiblyeligible for inclusion in the reimbursement program is anemployer-liable device 888 based on the job of employee 42. In theillustrated example, if an answer to a first question 890 of pluralityof questions 874 indicates to expense management system 16 that employee42 is required to travel outside of the United States more than fourtimes per year for business related purposes, or an answer to a secondquestion 892 indicates to expense management system 16 that employee 42is a division vice president or chief operating officer, then expensemanagement system 16 determines 876 that a mobile phone used by employee42 is treated as an employer-liable device 888.

Furthermore, in the exemplary embodiment, if employee 42 answers firstquestion 890 and second question 892 in the negative, and if an answerto a third question 894 indicates to expense management system 16 thatemployee 42 is a member of the customer field services team, expensemanagement system 16 determines 876 that employee 42 is eligible to havea reimbursement payment made on their behalf to a service provider, ordirectly to employee 42 (if that option was selected), at third level884. If employee 42 answers questions 890, 892, and 894 in the negative,and if an answer to a fourth question 896 indicates to expensemanagement system 16 that employee 42 is a member of the outside salesteam, expense management system 16 determines 876 that employee 42 iseligible to have a reimbursement payment made on their behalf to aservice provider, or directly to employee 42 (if that option wasselected) at third level 884.

Moreover, if employee 42 answers questions 890, 892, 894, and 896 in thenegative, and an answer to a fifth question 898 indicates to expensemanagement system 16 that employee 42 is responsible for a disasterrecovery team, pandemic team, or business continuity team, expensemanagement system 16 determines 876 that employee 42 is eligible to havea reimbursement payment made on their behalf to a service provider, ordirectly to employee 42 (if that option was selected), at second level882. Expense management system 16 may provide additional questions, forexample, questions 900, 902, 904, 906, and 908 in order to determine 876which level of reimbursement payment employee 42 is eligible to havemade on their behalf, or made directly to them (if that option wasselected).

FIG. 11 is a flow chart 950 of an exemplary method for processing 432 arequest for reimbursement from an employee, for example, employee 42(shown in FIG. 1). Prior to submitting a request for reimbursement,employee 42 has enrolled 422 (shown in FIG. 6) in the reimbursementprogram. In the exemplary embodiment, expense management system 16provides 960 employee 42 with a log in webpage that allows employee 42to enter a wireless device request for reimbursement portal. Forexample, expense management system 16 may provide employee 42 with alink to the request for reimbursement portal. That link may be accessedby employee 42 via the “My Account Page” described with respect to FIG.8. Expense management system 16 determines 962 whether an employeeaccount has been registered and activated for employee 42 (i.e., awireless profile record exists for employee 42). If expense managementsystem 16 determines 962 that a wireless profile record exists foremployee 42, expense management system 16 determines 964 whether awireless device is registered for employee 42. If a wireless profilerecord does not exist for employee 42, or no wireless device isregistered for employee 42, employee 42 is returned to the log inwebpage.

In the exemplary embodiment, if a wireless device is registered foremployee 42, expense management system 16 receives 966 a reimbursementrequest from employee 42. For example, expense management system 16 mayprovide 968 employee 42 with a “create reimbursement request” webpage.Once employee 42 selects 970 a reimbursement request from a requestslist provided by expense management system 16, employee 42 is able toenter information requested by expense management system 16. Theinformation provided by employee 42 within the reimbursement request mayinclude payment information associated with an employee-liable device.For example, expense management system 16 may receive 972 a deviceselection from employee 42, receive 974 payment information associatedwith the device selection, and/or receive 976 custom data provided byemployee 42. More specifically, the payment information may include, butis not limited to, the name of the service provider associated with thedevice, contact information for the service provider associated with thedevice, an account identifier associated with an account with theservice provider associated with employee 42 and/or the device, and/orany other information that may be used by expense management system 16to electronically direct a payment to the account with the serviceprovider associated with employee 42, or (if a direct employee paymentoption is selected) a payment directly to employee 42 or an accountassociated with employee 42.

Once the requested payment information is provided, expense managementsystem 16 receives 980, from employee 42, a request to create thereimbursement request. Expense management system 16 captures 982 therequest to create the reimbursement request and provides employee 42with the option to print/e-mail 984 the request for reimbursement,review 986 open requests for reimbursement, and/or log out 988 of therequest for reimbursement portal.

Furthermore, in the exemplary embodiment, expense management system 16requests 990 approval of the request for reimbursement from employer 20.For example, once expense management system 16 receives 980 a request tocreate the reimbursement request, system 16 transmits 1000 anotification to employer 20 that a request for reimbursement isavailable for review. More specifically, in the exemplary embodiment,system 16 transmits 1000 the notification to a manager of employee 42.As described above, during registration, a manager identifier isprovided of a person who has authority to approve requests forreimbursement submitted by employee 42 (see FIG. 8).

The manager logs in 1002 to expense management system 16, and morespecifically, to a “manager approval” webpage. Through the “managerapproval” webpage, the manager may access 1004 a list of requests forreimbursement awaiting review. Furthermore, the manager may provide 1006an approval or denial for each of the requests for reimbursement in thelist. Expense management system 16 determines 1008 if a request wasapproved or denied, and if a request is approved, the approved requestfor reimbursement is provided 1010 to an administrator of expensemanagement system 16 for review. After receiving an approval or denialfrom the manager, expense management system 16 again provides the listof requests for reimbursement awaiting review to the manager so themanager can review the remaining requests.

FIG. 12 is a flow chart 1020 of an exemplary method for initiating 1022recurring reimbursement program payments. As described above, requestsfor reimbursement are provided 1010 to an administrator of expensemanagement system 16 for review once the request for reimbursement isapproved by employer 20. In the exemplary embodiment, initiating 1022recurring reimbursement program payments includes reviewing 1024approved requests for reimbursement and creating 1026 a reimbursementrecord associated with an employee. For example, an administrator ofexpense management system 16 may review 1024 an approved request forreimbursement submitted by employee 42 and create 1026 a reimbursementrecord within the employee record associated with employee 42. In theexemplary embodiment, the reimbursement record includes the informationneeded to make payments to a service provider account associated withemployee 42, for example, but not limited to, an amount and frequency ofpayment, a service provider master account identifier, and/or a serviceprovider account identifier. In the exemplary embodiment, the serviceprovider master account identifier corresponds to a service provider,for example, service provider 30 (shown in FIG. 1). Furthermore, in theexemplary embodiment, the service provider account identifiercorresponds to an individual employee's account with service provider30. In other words, each service provider account is a sub-account of aservice provider master account. In order to enable an option for directemployee payment to be exercised, the reimbursement record will alsocontain employee account information if payments are to be madeelectronically to employee 42 or address and other information that maybe necessary if payments are to be made to employee 42 by check.

In the exemplary embodiment, expense management system 16 will requestapproval of payments, and make payments to service providers, associatedwith employees who have a reimbursement record included within theiremployee records, or make payments directly to employees who have areimbursement record included within their employee records, and withrespect to whom the direct employee payment option has been exercised.More specifically, once a reimbursement record associated with employee42 is created, expense management system 16 will submit an invoice toemployer 20 on a periodic basis that includes the payment requested byemployee 42 in the approved request for reimbursement. For example,expense management system 16 may submit an invoice to employer 20 onceevery month requesting approval of the payment requested by employee 42.

To facilitate reviewing 1024 approved requests for reimbursement,expense management system 16 may provide 1010 the administrator with an“administrator review” webpage. For example, the administrator mayaccess 1030 a list of reimbursement requests through the “administratorreview” webpage. Furthermore, the administrator may access 1032 theapproved reimbursement requests through the “administrator review”webpage. In the exemplary embodiment, reviewing 1024 includes reviewing1036 the employee identifier, device identifier, name of the serviceprovider, service provider account identifier, and/or other informationincluded within the request for reimbursement.

In the exemplary embodiment, to create 1026 a reimbursement record, theadministrator is provided 1040 with access to a “manage employees”webpage. For example, to create 1026 the reimbursement record, theadministrator adds the reimbursement record to the employee recordassociated with employee 42. More specifically, to create 1026 thereimbursement record, the administrator selects 1042 employee 42 and adevice associated with employee 42 that has been registered in thereimbursement program and adds the device identifier associated with thedevice and/or the service provider account identifier associated withthe device, to the reimbursement record. The administrator also selects1044 a reimbursement level that employee 42 is eligible to havereimbursed. This level may be determined 430 as described above withrespect to FIG. 10. The administrator also selects 1044 a serviceprovider master account identifier corresponding to the service provideremployee 42 named as the service provider associated with the device.For example, employee 42 may indicate in the request for reimbursementthat they have an employee-liable service provider account with ServiceProvider A. The administrator selects 1044 the service provider masteraccount identifier predefined as corresponding to Service Provider Awithin expense management system 16 and it is included within thereimbursement record. Typically, in an invoice generated by a serviceprovider, the service provider provides a service provider identifierused for recordkeeping and to aid in submission of payments to theservice provider. However, as is described further below, expensemanagement system 16 does not have access to the invoices associatedwith employee-liable devices. To facilitate generating invoices, andassociated records, expense management 16 assigns a predefined masteraccount identifier to each service provider included in reimbursementrequests from employees of employer 20. Although described above as amanual data entry process performed by the administrator, creating 1026the reimbursement record may be performed automatically by expensemanagement system 16. Alternatively, if the option has been selected foremployee 42 to be reimbursed directly, the administrator selects 1044 anemployee account identifier associated with an employee account whichemployee 42 has designated for receipt of reimbursement payments.

Once the administrator enters the information necessary to create thereimbursement record within the employee record, the administratorselects 1046 an “approve reimbursement” option and the reimbursementrecord is created. The reimbursement records may be reviewed 1048 and/ora notification may be transmitted 1050 to employee 42 indicating thatthe reimbursement record has been created.

FIG. 13 is a flow chart 1080 of an exemplary method for distributing 434(see FIG. 6) payments to employee-liable service provider accounts oremployee accounts, in the case of direct employee reimbursement. Asdescribed above, employee 42 is liable for expenses related to servicesprovided to employee 42 by service provider 30. Employee 42 hasregistered with service provider 30 and has been assigned a serviceprovider account, identified by a first service provider accountidentifier, to track payments made to the service provider and amountsowed to the service provider for services rendered. Similarly, secondemployee 44 has registered with service provider 32 and has beenassigned a service provider account, identified by a second serviceprovider account identifier. Furthermore, third employee 46 hasregistered with service provider 34 and has been assigned a serviceprovider account, identified by a third service provider accountidentifier. Moreover, as described above, typically a first plurality ofemployees will be party to contracts with service provider 30, a secondplurality of employees will be party to contracts with service provider32, and a third plurality of employees will be party to contracts withservice provider 34. Each of the employees included within first,second, and third plurality of employees will be assigned a serviceprovider account and associated service provider account identifier.These service provider account identifiers allow expense managementsystem 16 to apply reimbursement amounts to the intended account witheach service provider. Alternatively, each of the employees for whom adirect payment option applies, will provide an employee account and anemployee account identifier. These employee account identifiers willlikewise enable expense management system 16 to apply reimbursementamounts with the intended employee account associated with eachemployee.

In the exemplary embodiment, distributing 434 payments toemployee-liable service provider accounts includes generating 1100 aninvoice. Since the expenses reimbursed using expense management system16 are employee-liable expenses, invoices detailing amounts owed to theservice provider for services rendered are provided to the employee thatis liable for the expenses. For example, service provider 30 will notsend an invoice to expense manager 14 or employer 20 that detailsamounts owed by employee 42, since, it is employee 42 who is liable forthe amount owed to service provider 30. Therefore, in order for expensemanager 14 to obtain approval of payments made associated with theemployee-liable reimbursement program, and for employer 20 to havedetailed records of payments made associated with the program, expensemanagement system 16 generates 1100 an invoice. Typically, an invoice isgenerated by the party who is owed a payment, however, to facilitatepayments to the service providers, without having access to the invoicesissued by the service providers, expense management system 16 generates1100 invoices of amounts and payments that will be made as part of theprogram, rather than amounts actually owed to the service providers.

In the exemplary embodiment, expense management system 16 generates 1100the invoice based on the reimbursement records included within theemployee records (see FIG. 12 for creation of the reimbursementrecords). As described above, once a manager approves a reimbursementrequest from an employee, an administrator creates a reimbursementrecord within the employee's record. Expense management system 16accesses the reimbursement records and generates 1100 the invoice. Theinvoice may be a single invoice that includes all payments scheduled forpayment within a predefined time period, for example, the upcomingmonth, associated with approved reimbursement requests.

In the exemplary embodiment, the invoice is provided 1102 to employer 20in an electronic format, for example, expense management system 16 mayprovide 1102 employer 20 with access to a webpage. The webpage mayprovide 1102 employer 20 with options on how to organize the dataincluded within the invoice. For example, employer 20 may be able toorganize the invoice to view expenses associated with a specific serviceprovider master account identifier or employee account identifier. Morespecifically, employer 20 may be able to view and approve a total amountthat expense management system 16 is to pay to all the service providersor employees over the predefined time period or employer 20 may be ableto view and approve individual amounts that expense management system 16is to pay to first service provider 30, second service provider 32,and/or third service provider 34, and/or to employee 42, employee 44,and/or employee 46. Although described as a single invoice, thecustomization of the invoice provided by expense management system 16allows employer 20 to request and receive multiple invoices that includea more detailed description of the amounts to be paid by expensemanagement system 16 and to analyze the reimbursement program data in anumber of ways. Employer 20 may also be able to organize the invoice toview expenses associated with each individual employee having a serviceprovider account or employee account that is scheduled to receive fundswithin the predefined time period pending approval by employer 20.

Furthermore, expense management system 16 may provide other dataassociated with the reimbursement program to employer 20. For example,expense management system 16 may provide data to employer 20 thatidentifies a portion of the payment amount included in the invoice thatis associated with a specific cost center within employer 20. Expensemanagement system 16 may also provide data to employer 20 thatidentifies a portion of the payment amount that is associated with aspecific geographic location of the employees. The data provided byexpense management system 16 may include any other types of data thatfacilitate analysis of spending by employer 20 associated with thereimbursement program.

The data associated with the reimbursement program that is provided toemployer 20 may be provided in the form of a report. In the exemplaryembodiment, expense management system 16 stores data associated with thereimbursement program and accesses the data to generate historicalreports. Types of reports may include, but are not limited to: a reportdetailing payment information and payment history for an individualenrolled in the reimbursement program; a report detailing payments madeto a single service provider over a selectable time period; an IRUinventory report detailing all IRU devices, the employee associated witheach of the IRU devices, the geographical location of the employee, thecost center associated with the employee, the service provider providingservice to the employee, and a phone number associated with each of theIRU devices; and a report detailing corporate spending by serviceprovider and/or personal spending by service provider. These reports maybe customized by employer 20 and/or employee 42, for example, to show ahistorical spending trend over a selectable time period.

Moreover, in the exemplary embodiment, expense management system 16provides 1102 the invoice and/or other data to employer 20 in apredefined format that is compatible with record-keeping softwareutilized by employer 20. For example, the format may allow software ofemployer 20 to import records included within the invoice to a generalledger of employer 20. Furthermore, the format may be the same formatused to process invoices received that are associated withemployer-liable devices. For example, employer 20 may receive aninvoice, in a first format, from service provider 30 that includesamounts owed for use of employer-liable devices. In another example,employer 20 may receive invoices, in a first format, from expensemanagement system 16 for amounts owed for use of employer-liable devices(i.e., expense management system 16 may also manage payments to serviceproviders associated with employer-liable devices). Also providing theemployee-liable reimbursement program invoice in the first formatimproves integration of the employee-liable reimbursement program intothe day-to-day recordkeeping of employer 20.

In at least one embodiment, expense management system 16 provides 1102the invoice to employer 20 in a predefined format that is compatiblewith record-keeping software utilized by employer 20 and provides 1102other data to employer 20 using a web-based interface. For example,expense management system 16 may provide 1102 employer 20 with access toa webpage. The webpage may provide 1102 employer 20 with options on howto organize the data stored by expense management system 16 associatedwith employer 20. For example, employer 20 may be able to organize thedata to create the reports described above.

In the exemplary embodiment, expense management system 16 receives 1104approval of at least a portion the invoice from employer 20. Forexample, employer 20 may approve all payments included within theinvoice provided 1102 by expense management system 16. Alternatively,employer 20 may approve some of the payments included within theinvoice. Once expense management system 16 receives 1104 approval of atleast a portion of the invoice from employer 20, expense managementsystem 16 automatically requests funds from employer 20 to cover theapproved payments.

In the exemplary embodiment, expense management system 16 alsoelectronically transfers 1106 funds from an employer associated accountto the service providers associated with the approved payments, and/orto employees receiving direct reimbursement. More specifically, expensemanagement system 16 electronically transfers 1106 funds to the serviceprovider accounts associated with the approved employees, and/or to theemployee accounts associated with the approved employees. As describedabove, when approved, a reimbursement record is included within anemployee record. The reimbursement record includes the data necessaryfor expense management system 16 to direct payments to the serviceprovider accounts associated with the approved employees, including aservice provider account identifier. For example, expense managementsystem 16 may provide a payment associated with first employee 42 tofirst service provider 30, a payment associated with second employee 44to second service provider 32, and a payment associated with thirdemployee 46 to third service provider 34. Furthermore, when a pluralityof employees enrolled in the reimbursement program have service provideraccounts with first service provider 30, expense management system 16may provide a single payment to first service provider 30, withinstructions how to allocate that payment (e.g., a list of serviceprovider accounts in which to apply the funds, and an amount associatedwith each service provider account on the list). The transfer 1106 offunds includes transfers made under a direct payment option to employeeaccounts associated with approved employees. In the exemplaryembodiment, expense management system 16 electronically transfers 1106funds using ACH/CTX payment transactions.

In the exemplary embodiment, a plurality of employees, for example,employees 40 (shown in FIG. 1) are enrolled 422 (shown in FIG. 6) in theemployee-liable expense reimbursement program offered by their employer,for example, employer 20 (shown in FIG. 1). Requests for reimbursementsubmitted by employees 40 are processed 432 (shown in FIG. 6) by expensemanagement system 16 (shown in FIG. 1). Approval, by employer 20, of therequests for reimbursement, prompts expense management system 16, oralternatively, an administrator associated with expense manager 14, tocreate 1026 (shown in FIG. 12) a reimbursement record. Expensemanagement system 16 periodically generates 1100 (shown in FIG. 13) aninvoice based on the reimbursement records. For example, expensemanagement system 16 may generate 1100 an invoice, once each month, foreach of the service providers participating in the employee-liableexpense reimbursement program (e.g., one invoice per month for each ofservice providers 28, shown in FIG. 1). In at least one example, eachinvoice includes a total amount to be paid to the corresponding serviceprovider that month.

In the exemplary embodiment, expense management system 16 provides 1102the invoice to employer 20. For example, the invoice may requestapproval from employer 20 of a $30, 425 payment to be made to firstservice provider 30 (shown in FIG. 1). Once expense management system 16receives 1104 approval of this payment to first service provider 30,expense management system 16 requests that $30, 425 be funded, byemployer 20, to a financial account associated with expense manager 14within a predefined time period (e.g., two business days). In thisexample, expense management system 16 also creates and transmits an ACHtransaction for $30, 425 to first service provider 30, with CTXtransaction details that include instructions for first service provider30 as to which sub-accounts to apply the funds, and the amountassociated with each sub-account. In other words, the CTX transactiondetails created by expense management system 16 appear to first serviceprovider 30 as if expense management system 16 is paying one invoice foreach of employees 40 (e.g., possibly hundreds of individual invoices).In response to the ACH/CTX transaction submitted by expense managementsystem 16, first service provider 30 applies a payment credit equal tothe amount specified in the ACH/CTX transaction to each employee'spersonal account (i.e., their service provider account with firstservice provider 30). Any problem applying the funds is communicated byfirst service provider 30 to expense management system 16.

Described herein are exemplary methods and systems for managing paymentof employee-liable expenses. An expense management system administers aperiodic distribution of payments directly to a service provider, andmore specifically, directly to an account with the service providerassociated with an employee. Optionally, payments are made directly toemployees for employee-liable expenses associated with services providedby the service provider. More specifically, the methods and systemsdescribed herein allow administrators to configure various reimbursementlevels based on policies developed by an employer. The administratorselectronically invite employees to participate in the employer'semployee-liable device reimbursement program. Employees are directedthrough an online questionnaire process for the purposes of determiningeligibility, determining reimbursement level, and gaining managementapproval. The methods and systems described herein facilitateadministering a periodic distribution of payments directly to theservice providers electronically to approved employee-liable accountsvia ACH/CTX payment transactions. The methods and systems describedherein also facilitate reporting on the status of payments, what serviceproviders or employees were paid, how much each employee has paid ontheir behalf, where within the employer each payment is accounted for,and other reporting functions necessary for auditing the validity of theexpense. An inventory of devices is provided and a periodic validationof employee reimbursed devices and accounts is performed. An expensemanager may electronically request funds from the employer and providean automated general ledger upload file for recording employee-liabledevice payments. The systems and methods described herein also matchemployee-liable device payments to human resource records to ensurepayments are made only for valid employees.

The methods and systems described herein facilitate efficient andeconomical payment of employee-liable expenses. Exemplary embodiments ofmethods and systems are described and/or illustrated herein in detail.The methods and systems are not limited to the specific embodimentsdescribed herein, but rather, components of each system, as well assteps of each method, may be utilized independently and separately fromother components and steps described herein. Each component, and eachmethod step, can also be used in combination with other componentsand/or method steps.

When introducing elements/components/etc. of the methods and systemsdescribed and/or illustrated herein, the articles “a”, “an”, “the”, and“said” are intended to mean that there are one or more of theelement(s)/component(s)/etc. The terms “comprising”, “including”, and“having” are intended to be inclusive and mean that there may beadditional element(s)/component(s)/etc. other than the listedelement(s)/component(s)/etc.

This written description uses examples to disclose the invention,including the best mode, and also to enable any person skilled in theart to practice the invention, including making and using any devices orsystems and performing any incorporated methods. The patentable scope ofthe invention is defined by the claims, and may include other examplesthat occur to those skilled in the art. Such other examples are intendedto be within the scope of the claims if they have structural elementsthat do not differ from the literal language of the claims, or if theyinclude equivalent structural elements with insubstantial differencesfrom the literal language of the claims.

What is claimed is:
 1. A computer-based method for generating aplurality of data structures to enable electronic payments to aplurality of service providers as part of a program offered to employeesof an employer, each service provider associated with a data format forpayment of single billing communications that cover multiple accounts,said method implemented using a computer system that includes aprocessor and a memory, the memory having stored therein, for eachparticipating employee, (i) an identifier associated with one of theservice providers, and (ii) an identifier for an employee accountassociated with the identified service provider, wherein the employeeaccount is configured by the service provider for billing to theemployee, said method comprising: generating a first data fileassociated with a predefined time period, wherein the first data fileincludes data that identifies an aggregated amount to be paid by theemployer to each service provider within the predefined time period forapplication to the employee accounts associated with the respectiveservice provider, and wherein the first data file is generated withoutreceiving billing communications from the service providers;transmitting the first data file to the employer; receiving approvalfrom the employer for payment on at least a portion of each of theaggregated amounts included in the first data file; requesting fundsfrom the employer equal to at least a total of the respective approvedamounts to be paid to each service provider; generating, withoutreceiving billing communications from the service providers, theplurality of data structures associated with the predefined time period,each data structure corresponding to a respective service provider,wherein each data structure includes data that (i) designates fortransfer to the service provider funds equal to at least the approvedamount associated with the respective service provider, and (ii)instructs the service provider to allocate the designated funds amongthe employee accounts associated with the respective service providerbased on the associated employee account identifier and an amountassociated with each employee account, and wherein each data structureis in the data format associated with the respective service providerfor payment of single billing communications that cover multipleaccounts.
 2. A method in accordance with claim 1, wherein the memoryfurther has stored therein, for each participating employee, at leastone of a cost center and a geographic location assigned to the employeeby the employer, and wherein said generating the first data file furthercomprises identifying a portion of the total of the aggregated amountsas being associated with the at least one of the cost center and thegeographic location of the associated employees.
 3. A method inaccordance with claim 1, further comprising presenting the first datafile to the employer in an electronic format with organize functions,the organize functions enabling the employer to sort or reconfigure theprovided data to facilitate review of the requested funds.
 4. A methodin accordance with claim 3, wherein said presenting the first data filefurther comprises providing the employer with access to a webpage,wherein the webpage provides the employer with the organize functions.5. A method in accordance with claim 1, further comprising presentingthe first data file in an electronic format configured for importinginto an accounting system of the employer as a general ledger entry. 6.A method in accordance with claim 1, wherein the memory further hasstored therein, for each participating employee, a timing of a recurringpayment to be made on the identified employee account, said generatingthe first data file associated with the predefined time period furthercomprises generating the first data file based on the stored timing ofthe recurring payment for each participating employee.
 7. A method inaccordance with claim 1, further comprising storing the service provideridentifier and employee account identifier for at least oneparticipating employee based on electronic registration data receivedfrom the at least one participating employee.
 8. A method in accordancewith claim 7, further comprising requesting approval, from arepresentative associated with the employer, of the received electronicregistration data.
 9. A method in accordance with claim 1, wherein saidgenerating the plurality of data structures further comprises generatingthe plurality of data structures in a standard electronic paymenttransaction format.
 10. A method in accordance with claim 9, furthercomprising electronically transferring funds to each service provider inaccordance with the respective data structure.
 11. A method inaccordance with claim 1, wherein the computer system is in communicationwith a human resource (HR) computer system associated with the employer,and wherein said method further comprises: receiving, from the HRcomputer system, a third data file that includes a list of currentemployees of the employer; and verifying stored information for at leastone participating employee against the list.
 12. A method in accordancewith claim 1, wherein the computer system is in communication with ahuman resource (HR) computer system associated with the employer, andwherein said method further comprises: receiving, from the HR computersystem, employee data associated with at least one participatingemployee; determining the amount to be paid on the employee account ofthe at least one participating employee based at least in part on theemployee data; and storing the amount to be paid in the memory.
 13. Oneor more non-transitory computer-readable storage media havingcomputer-executable instructions embodied thereon for generating aplurality of data structures, wherein when executed by at least oneprocessor, the computer-executable instructions cause the processor to:generate a first data file associated with a predefined time period,wherein the first data file includes data that identifies an aggregatedamount to be paid by an employer to each of a plurality of serviceproviders within the predefined time period for application to aplurality of employee accounts associated with the respective serviceprovider, each service provider associated with a data format forpayment of single billing communications that cover multiple accounts,each employee account associated with a respective employeeparticipating in a program offered to employees of the employer, whereinthe processor is coupled to a memory, the memory having stored therein,for each participating employee, (i) an identifier associated with oneof the service providers, and (ii) an identifier for the employeeaccount associated with the identified service provider, wherein theemployee account is configured by the service provider for billing tothe employee, and wherein the first data file is generated withoutreceiving billing communications from the service providers; transmitthe first data file to the employer; receive approval from the employerfor payment on at least a portion of each of the aggregated amountsincluded in the first data file; request funds from the employer equalto at least a total of the respective approved amounts to be paid toeach service provider; generate, without receiving billingcommunications from the service providers, the plurality of datastructures associated with the predefined time period, each datastructure corresponding to a respective service provider, wherein eachdata structure includes data that (i) designates for transfer to theservice provider funds equal to at least the approved amount associatedwith the respective service provider, and (ii) instructs the serviceprovider to allocate the designated funds among the employee accountsassociated with the respective service provider based on the associatedemployee account identifier and an amount associated with each employeeaccount, and wherein each data structure is in the file formatassociated with the respective service provider for payment of singlebilling communications that cover multiple accounts.
 14. Thecomputer-readable storage media in accordance with claim 13, wherein thememory further has stored therein, for each participating employee, atleast one of a cost center and a geographic location assigned to theemployee by the employer, and wherein the computer-executableinstructions cause the processor to identify in the first data file aportion of the total of the aggregated amounts as being associated withthe at least one of the cost center and the geographic location of theassociated employees.
 15. The computer-readable storage media inaccordance with claim 13, wherein the computer-executable instructionscause the processor to present the first data file to the employer in anelectronic format with organize functions, the organize functionsenabling the employer to sort or reconfigure the provided data tofacilitate review of the requested funds.
 16. The computer-readablestorage media in accordance with claim 13, wherein thecomputer-executable instructions cause the processor to present thefirst data file in an electronic format configured for importing into anaccounting system of the employer as a general ledger entry.
 17. Thecomputer-readable storage media in accordance with claim 13, wherein theprocessor is in communication with a human resource (HR) computer systemassociated with the employer, and wherein the computer-executableinstructions cause the processor to: receive, from the HR computersystem, a list of current employees of the employer; and verify storedinformation for at least one participating employee against the list.18. The computer-readable storage media in accordance with claim 13,wherein the processor is in communication with a human resource (HR)computer system associated with the employer, wherein thecomputer-executable instructions cause the processor to: receive, fromthe HR computer system, employee data associated with at least oneparticipating employee; determine the amount to be paid on the employeeaccount of the at least one participating employee based at least inpart on the employee data; and store the amount to be paid in thememory.